Havish M Consulting
Customer Case Study · Sales Reimbursement Audit
Cement Manufacturing × Havish M Consulting

Every bill read, every rupee checked, every location verified

Field sales teams submit hundreds of hotel, meal, fuel and travel bills each month: thermal printouts, handwritten Hindi cash memos and phone photos. HMC built a reimbursement audit desk for the cement company's Finance team that reads each bill, checks it against the salesperson's entitlement and approved tour plan, and confirms the bill came from inside their geo-fenced beat.

ClientCement Manufacturing FunctionFinance · Sales Expenses ThemeBill Reading & Geo-fenced Audit
Bills checked against policy
0%
▲ from about 1 in 10 sampled
Claim value held back as out of policy
0%
▲ caught before payment
Days from submission to settlement
0days
▼ from about 18 days
Bills read without manual typing
0%
▲ incl. handwritten Hindi memos

Figures indicative; validated metrics available on request.

The Challenge

A shoebox of bills, checked by sampling

Sales officers and managers travel across their beats every week. Finance had to settle their claims quickly, fairly and within policy, with only paper and photos to go on.

Bills in every format

Faded thermal slips, handwritten Hindi cash memos and blurry phone photos, all typed in by hand.

Entitlements in a PDF

Caps differ by grade and city tier. Checking each bill against the right cap took time, so most were not.

No way to check where

A dinner bill 200 km from the approved beat looked the same as one next door.

Slow, uneven settlement

Claims waited weeks; deductions arrived without reasons and salespeople pushed back.

HMC Approach

Policy first, then the reader, then the map

We turned the travel policy into rules a computer can apply, taught it to read every bill format the field sends, and added location as a check.

Select a step to see what happened.

Discover · What a claim really looks like

Three months of claims, bills and deductions reviewed with the finance team.

  • Bill formats: GST invoices, cash memos, fuel slips, cab and rail tickets.
  • Where money leaked: over-cap stays, duplicate bills, off-beat meals.
  • Why settlements were slow and disputed.

Deliverable: Leakage map and bill format library.

Design · Policy as rules

Every line of the travel policy written as a check.

  • Caps by grade (M1 to M3) and city tier (A, B, C).
  • Tour plan and geo-fence radius per beat.
  • Clear outcomes: approve, approve to cap, hold, reject, each with a reason.

Deliverable: Rulebook signed off by Finance and Sales.

Build · Reader, checks and map

From photo to decision in seconds.

  • GenAI vision reads printed and handwritten bills, Hindi included.
  • GSTIN check digit, arithmetic, duplicates and dates.
  • Vendor address geocoded and matched to the beat fence and GPS check-ins.

Deliverable: Audit desk and claim register.

Adopt · Finance stays in charge

The desk recommends; Finance decides.

  • Pilot in two zones with weekly settlement.
  • Every deduction comes with a plain-English reason.
  • Holds go back to the salesperson with what is needed.

Deliverable: Pilot results and SOP.

Scale · All sales teams

Same rules for everyone.

  • All zones and grades.
  • Field app sends bills and GPS check-ins together.
  • Approved claims post to the ERP for payment.

Deliverable: Roll-out and monthly audit pack.

The Solution

Run the reimbursement audit desk

Seventeen sample bills from four salespeople for one October week. Read a bill, see how it is checked against entitlement and tour plan, and see where it was issued on the map. Upload your own bill with an OpenAI key.

✦ Read real bills with GenAI

Optional. Without a key, the demo reads the sample bills and pulls details out of pasted bill text with rules. Add your OpenAI key to read photos of any bill, printed or handwritten, Hindi included, and to draft deduction notes.

Templates
Your key goes only from this browser to OpenAI. Bills you upload stay in this page.
01 · Bill reader

From a photo to a structured bill

Pick a sample bill and press Read, or upload a photo of your own. Every field is pulled out with a confidence score, and every bill read lands in the table below, ready for CSV.

Templates

Sample bills · Oct week 41

Or paste bill text

Claim new bills under

Sample bill

Extracted details

Line items

Extracted bills · 0

#SourceSalespersonVendorCityBill noDateCategoryGSTINItemsTax ₹Total ₹Decision

Synthetic sample bills: vendors, GSTINs, people and amounts are illustrative. Uploaded bills are sent only to OpenAI with your key and are not stored.

02 · Entitlement check

Each bill against the salesperson's policy

Caps depend on grade and city tier; meals are capped per day; bills must match the approved tour plan. Open a bill to see all nine checks. Move a cap and every decision updates.

DateBillClaimedEligibleDisallowedChecksDecision

Synthetic policy and people. Checks: ① read ② arithmetic ③ GSTIN ④ entitlement cap ⑤ tour plan date ⑥ geo-fence ⑦ duplicate ⑧ submission window ⑨ non-reimbursable items.

03 · Geo-fence

Was the bill issued inside the approved beat?

Each fence is a circle around a town in the day's approved tour plan. Bill pins sit at the vendor's address; small dots are GPS check-ins from the field app. Green pins are inside the fence for that day, red pins are outside.

Bills by distance from fence

Vendor addresses are geocoded (Google Maps Places in production; a built-in gazetteer of UP towns in this demo). "Open in Google Maps" on each pin shows the exact spot.

04 · Finance desk

Settle the week, with a reason for every rupee

The claim register shows what is payable now, what is held for an answer and what is disallowed. Draft the note each salesperson receives, from templates or with GenAI.

Templates

Claim register · week 41

Payable nowHeld for answerDisallowed

Choose a salesperson and draft the settlement note.

The desk recommends; Finance approves every claim before payment.

Impact Dashboard

Every rupee checked, and paid faster

Finance moved from sampling one claim in ten to checking every bill, and settles within days instead of weeks.

Where ₹100 of claims goes

Sankey: claim value through checking to outcome

Claimed, entitled, paid, days

Parallel coordinates: one line per claim

Paid in fullPaid to capRejectedBefore: paid as claimed

Figures indicative; validated metrics available on request.

Before vs After

How sales claims are audited now

DimensionBeforeAfter
Reading billsTyped in by handRead from the photo, Hindi included
CoverageAbout 1 in 10 sampledEvery bill, every claim
EntitlementLooked up in a PDF, sometimesCap by grade and city tier, applied automatically
LocationNot checkedVendor address against beat fence and GPS
DeductionsDisputed, no reason givenItemised note with the rule behind each one
SettlementAbout 18 daysAbout 3 days
Tools & Tech Used

The audit desk stack

OpenAI GPT-4o vision bill reading Google Maps Places vendor geocoding Leaflet + OpenStreetMap geo-fence map Rules engine entitlement and GSTIN checks Power Automate claim workflow SAP FI posting approved claims
Key Takeaways

What any finance team can borrow

01

Write the policy as rules first

Once caps, tiers and windows are rules, checking every bill costs the same as checking one.

02

Location is a cheap, strong check

A vendor address plus the day's tour plan answers "was this on the beat?" without accusing anyone.

03

Give a reason with every deduction

Disputes drop when the salesperson sees the rule, the cap and the amount, line by line.